Application-launching interface for multiple modes

ABSTRACT

This document describes techniques and apparatuses enabling an application-launching interface for multiple modes. This interface enables a user to quickly and easily select to launch applications associated with different modes. A user may avoid wading through multiple interfaces, making multiple selections, and/or a cognitive load associated with deciding on a mode with which to interact.

BACKGROUND

Many conventional application-launching interfaces permit users tolaunch applications into a windows-based mode. Most windows-based modespresent a launched application with a frame having controls forinteracting with the application as well as controls for moving, sizing,or otherwise managing the layout of the window frame. This window frame,however, occupies part of a display that might otherwise be dedicated tothe application's content. If a user wishes to launch an applicationinto an immersive or other non-windows-based mode, such as to avoid awindow frame, the user typically first selects to launch a secondarylaunching application from within the conventional interface, waits forthe secondary launching application to launch within the windows-basedmode, views other applications within the secondary launchingapplication's window frame, selects one of these other applications, andthen waits for that other application to be launched within thenon-windows-based mode.

Some other conventional application-launching interfaces permit users tolaunch applications directly into an immersive mode. These otherconventional application-launching interfaces, however, launchapplications only into the immersive mode. Most immersive modes permit auser to view and interact with more of an application's content thanthat of the windows-based mode, though they lack much of the flexibilitypermitted by the windows-based mode.

SUMMARY

This document describes techniques and apparatuses enabling anapplication-launching interface for multiple modes. This interfaceenables a user to avoid having to use multiple interfaces, make numerousselections, or know where and how to launch applications into differentmodes.

This summary is provided to introduce simplified concepts for anapplication-launching interface for multiple modes that are furtherdescribed below in the Detailed Description. This summary is notintended to identify essential features of the claimed subject matter,nor is it intended for use in determining the scope of the claimedsubject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of techniques and apparatuses for an application-launchinginterface for multiple modes are described with reference to thefollowing drawings. The same numbers are used throughout the drawings toreference like features and components:

FIG. 1 illustrates an example system in which techniques enabling anapplication-launching interface for multiple modes can be implemented.

FIG. 2 illustrates an example method enabling an application-launchinginterface for multiple modes.

FIG. 3 illustrates an example application-launching interface havingselectable labels for various applications of different modes.

FIG. 4 illustrates the example application-launching interface of FIG. 3along with an example gesture selection of a selectable label associatedwith an immersive-mode application.

FIG. 5 illustrates the immersive-mode application of FIG. 4 launchedinto an immersive mode.

FIG. 6 illustrates an example application-launching interface having twoselectable groups of applications.

FIG. 7 illustrates an example display split into two portions, oneportion having an immersive mode and the other having a windows-basedmode in which applications selected through the application-launchinginterface of FIG. 6 are presented.

FIG. 8 illustrates an example application-launching interface havingselectable labels for groups of applications and presentation ofselectable labels for applications of a selected group.

FIG. 9 illustrates an example device in which techniques enabling anapplication-launching interface for multiple modes can be implemented.

DETAILED DESCRIPTION Overview

This document describes techniques and apparatuses enabling anapplication-launching interface for multiple modes. This interfaceenables a user to quickly and easily select to launch applicationsassociated with different modes. A user may avoid wading throughmultiple interfaces, making multiple selections, and/or a cognitive loadassociated with deciding on a mode with which to interact.

Assume, for example, that a user wishes to begin her workday with fourapplications, two of which are windows-based and two of which areimmersive. Conventional techniques may require her to select awindows-based application-launching interface, select to launch thefirst of the two windows-based applications, wait for it to launch, thenreturn to the interface, select to launch the second of the twowindows-based applications, and then wait for the second application tolaunch. With these two launched, the user then either opens an immersiveapplication-launching interface or launches an application or secondarylaunching interface through the windows-based application-launchinginterface. In either case, the user then selects a first of the twoimmersive applications, waits for it to launch, returns to the immersiveapplication-launching interface (or windows-based application capable oflaunching into the immersive mode), selects the second application, andthen waits for the second application to launch.

As is readily apparent, this is time consuming for the user. It alsorequires the user to know from which of the interfaces or launch-capableapplications to launch the four applications. This knowledge is anexample of cognitive load, which is often considered a factorcontributing to a poor user experience.

The techniques, however, permit the user to select to launch all fourapplications through a single interface, thereby reducing the user'scognitive load and effort. Furthermore, the techniques also permitselection of each application with a single selection or even, in somecases, multiple applications with a single selection, therebysignificantly reducing the time and/or cognitive load needed to launchapplications.

Example System

FIG. 1 illustrates an example system 100 in which techniques enabling anapplication-launching interface for multiple modes can be embodied.System 100 includes a computing device 102, which is illustrated withsix examples: a laptop computer 104, a tablet computer 106, a smartphone 108, a set-top box 110, a desktop computer 112, and a gamingdevice 114, though other computing devices and systems, such as serversand netbooks, may also be used.

Computing device 102 includes computer processor(s) 116 andcomputer-readable storage media 118 (media 118). Media 118 includes anoperating system 120, windows-based mode module 122, immersive modemodule 124, launcher 126, and applications 128, each of which mayprovide content 130. Computing device 102 also includes or has access toone or more displays 132, four examples of which are illustrated in FIG.1.

Windows-based mode module 122 presents at least some of applications 128and accompanying content 130 through windows having frames. These framesmay provide controls through which to interact with an applicationand/or controls enabling a user to move and size the window.

Immersive mode module 124 provides a mode by which a user may view andinteract with one or more of applications 128 and corresponding content130. In some embodiments, this mode presents content of, and enablesinteraction with, applications with little or no window frame and/orwithout a need for a user to manually size or position content. Thismode can be, but is not required to be, hosted and/or surfaced withoutuse of a typical desktop (e.g., windows-based) mode. Thus, in some casesimmersive mode module 124 presents an immersive mode that is not awindow (even one without a substantial frame) and precludes usage ofdesktop-like displays (e.g., a taskbar). Further still, in someembodiments this immersive mode is similar to an operating system inthat it is not closeable or capable of being un-installed. Examples ofimmersive modes are provided below as part of describing the techniques,though they are not exhaustive or intended to limit the techniques.

Launcher 126 provides an application-launching interface that permitsselection to launch applications of different modes, such aswindows-based and immersive modes, though other modes are alsopermitted. In some embodiments, launcher 126 permits selection topresent applications that are currently executing. Thus, launcher 126can enable a user to select applications of different modes to launchinto a respective mode or to be presented in a respective mode, based onwhether the applications is not or is currently executing, respectively.Note that a user may or may not be aware of which applications arecurrently executing and may not notice a difference between selecting anapplication that is or is not executing, as in both cases theapplication is shown in its respective mode responsive to beingselected.

Operating system 120, mode modules 122 and 124, and launcher 126 can beseparate from each other or combined or integrated in some form. Thus,in some cases operating system 120 includes mode modules 122 and 124 andlauncher 126.

Example Methods

FIG. 2 depicts a method 200 for an application-launching interface formultiple modes. This method is shown as a set of blocks that specifyoperations performed but is not necessarily limited to the order shownfor performing the operations by the respective blocks. In portions ofthe following discussion reference may be made to system 100 of FIG. 1,reference to which is made for example only.

Block 202 presents, in a single user interface and/or at one time,labels associated with applications of two different modes. Thesedifferent modes may include windows-based and immersive modes, thoughother modes are also permitted by the techniques. Each label isassociated with an application and indicates this association, such aswith a graphic or textual descriptor. Applications are selectable, insome cases, through these labels, such as through a mouse click orgesture (e.g., through a touch-screen implementation of display 130). Insome cases, however, the applications are selectable as a group and/orthrough a hot key or other selection manner other than directly througha label.

Consider example application-launching interface 300 of FIG. 3, whichillustrates selectable labels for various application of differentmodes. Here launcher 126 of FIG. 1 provides interface 300 having 15selectable labels associated with applications of two modes—awindows-based mode and an immersive mode.

Note that applications of these different modes are intermixed withininterface 300, namely immersive-mode applications having labels 302,304, and 306 and windows-based-mode applications have labels 308, 310,and 312. Further, consider in greater detail label 308, whichillustrates optional windows indicator 314 and immersive indicator 316.Optional indicators 314 and 316 are completely optional. Theseindicators do not need to be presented within interface 300.

While not shown in interface 300 (except in label 308), any of thelabels of interface 300 may include an indicator showing which mode intowhich they will be launched on selection. This is of interest to someusers but not others. Further still, applications that are currentlyexecuting and not currently executing may also be intermixed andoptionally include an indicator showing whether they are executing. Asnoted above, launcher 126 enables selection of executing andnon-executing application through a same interface, either differentlyor with a same type of selection.

In some example cases, an application may be launched into multiplemodes. A mode for launch may be selected by launcher 126 by default,though it may also enable a user to select which mode, here by selectingone of indicators 314 or 316. This is but one example of ways in which asingle selection may launch an application differently based on thatselection.

Block 204 receives a selection. As noted, selection of one or moreapplications can be made in various manners, including a singleselection to launch one application or even a single selection to launchmultiple applications. Continuing the ongoing example, considerselection of the immersive-mode application associated with label 304 ofFIG. 3. Selection here is received through a gesture 402 shown in FIG.4. Note that this single selection made through gesture 402 selects thecontent that is to be displayed when the application is launched. Thisis another example of reducing a user's effort and cognitive load, inthis case by launching directly to desired content.

Block 206, responsive to selection, causes the selected application(s)to launch within respective mode(s). Before proceeding to coverlaunching multiple applications with a single selection, consider theongoing embodiment in which a user selected, through gesture 402 ofselectable label 304 associated with the application, to launch this“News” application. As noted, this application is associated with animmersive mode. Thus, in response to receiving the gesture, launcher 126causes the News application to launch. Here launcher 126 does so bypassing this selection on to immersive mode module 124. Immersive modemodule 124 launches the News application. FIG. 5 illustrates an exampleof this launch on display 500 into immersive mode 502 with content 504of the News application. The News application is one example ofapplications 128, display 500 of display 132, and content 504 of content130, all of FIGS. 1 and 5.

By way of another example, consider a second selection through interface300, this selection through the same gesture as illustrated in FIG. 4but selecting instead a word-processing application associated with awindows-based mode and selected through windows-based label 310 of FIG.3 (selection not shown). Responsive to receiving this selection,launcher 126 launches the word-processing application into awindows-based mode by passing this selection to windows-based modemodule 122 of FIG. 1. Note that applications of different modes areselectable through the same type of selection, though this is notrequired. Doing so permits a user to avoid the cognitive load of havingto know two different selection manners for these two different modes.The windows-based mode is not illustrated for this example but isillustrated later below in the context of launching multipleapplications with a single selection.

Launcher 126 may also or instead present labels in groups and/or enableselection of multiple applications. Note that these groups and selectionof multiple applications through a single selection is completelyoptional. Consider application-launching interface 600 of FIG. 6. Inthis case, launcher 126 (performing block 202 of FIG. 2), presentsinterface 600 having two selectable groups of applications, a “Work”group shown at 602 and a “Play” group shown at 604. The applicationsassociated with each of these groups may be determined based on a user'sselection or history, to name a few. A user's history can include howoften, when, and how applications are used, for example. In thisillustration, the applications are grouped based on a user's explicitselection to create these groups, which may be enabled by launcher 126through a graphical selection of labels to create a group.

Group 602 includes four selectable labels 606, 608, 610, and 612associated with four applications, two of which are windows-based andtwo of which are immersive. Group 604 includes seven selectable labels614, 616, 618, 620, 622, and 624 associated with seven applications, oneof which is windows based and six of which are immersive. Thus, each ofthese groups 602, 604 includes at least one application associated witheach of both different modes and presents them intermixed, in a sameinterface, and at a same time.

Continuing this example, launcher 126 receives a gesture selection 626to the Work group 602 made to a non-label area 628. At block 206,launcher 126 causes all of the applications in the group to be launchedwith this single selection. Here launcher 126 causes these launches witha command to launch each application made to each application'srespective mode module (windows-based mode module 122 or immersive modemodule 124 of FIG. 1). These multiple application launches into multiplemodes are illustrated in FIG. 7, which provides example display 700split into two portions, one for the immersive applications at 702 andthe other for the windows-based applications at 704. Note that in thisexample the two windows-based applications are launched, though one islaunched with content and the other is launched but awaits selection topresent content. Similarly, both immersive applications are launchedwith one presenting content and the other awaiting further selection.

Other manners of presenting applications responsive to selection throughthe interface are also possible, such as presenting one mode butlaunching applications of two modes, launching applications of one modeand presenting just that mode and, responsive to a selection to switchto the other mode, automatically launching the other applications andpresenting the other mode. In some cases a group permits still otherfunctions, such as selection by a user to automatically launchapplications of a group without further user selection but responsive tosome change.

Thus, launcher 126 may automatically launch applications (e.g., those ofwork group 602 or play group 604) responsive to numerous conditions,such as a user logging into computing device 102 on a weekday or on aweekend. Other conditions include, by way of example and not limitation,resuming computing device 102 from a low-power mode (e.g., sleep orhibernation), movement of computing device 102 (e.g., to a dockingstation at work or within range of a wireless network at home), auser-configured trigger (e.g., an event capable of being tracked orreceived by computing device 102), and a pre-set time (e.g., 9 am).

By way of still another example, consider a different type of selectionof a group, this time through application-launching interface 800 ofFIG. 8. In this example, interface 800 presents labels 802 and 804 forselecting groups, here label 802 for Work group 602 and label 804 forPlay group 604 of FIG. 6. As noted above, launcher 126 may launch all ofthe applications of Work group 602 with a single selection. Herelauncher 126 may do so without explicitly showing labels associated withall of those applications. Thus, selection of label 802 may cause allapplications of the Work group 602 to launch. Alternatively, selectionof a group label may instead present all of the labels of theapplications. In this alternate embodiment, launcher 126 presentsselectable labels associated with applications of Work group 602 at 806responsive to selection 808 shown in FIG. 8. With these presented,selection of one, multiple, or all of the applications may be made asnoted above.

The preceding discussion describes methods in which the techniques mayoperate to enable an application-launching interface for multiple modes.Aspects of these methods may be implemented in hardware (e.g., fixedlogic circuitry), firmware, software, manual processing, or anycombination thereof A software implementation represents program codethat performs specified tasks when executed by a computer processor. Theexample methods may be described in the general context ofcomputer-executable instructions, which can include software,applications, routines, programs, objects, components, data structures,procedures, modules, functions, and the like. The program code can bestored in one or more computer-readable memory devices, both localand/or remote to a computer processor. The methods may also be practicedin a distributed computing mode by multiple computing devices. Further,the features described herein are platform-independent and can beimplemented on a variety of computing platforms having a variety ofprocessors.

These techniques may be embodied on one or more of the entities shown inenvironment 100 of FIG. 1 and/or example device 900 described below,which may be further divided, combined, and so on. Thus, environment 100and/or device 900 illustrate some of many possible systems orapparatuses capable of employing the described techniques. The entitiesof environment 100 and/or device 900 generally represent software,firmware, hardware, whole devices or networks, or a combination thereofIn the case of a software implementation, for instance, the entities(e.g., launcher 126, mode modules 122 and 124) represent program codethat performs specified tasks when executed on a processor (e.g.,processor(s) 116). The program code can be stored in one or morecomputer-readable memory devices, such as computer-readable storagemedia 118 or computer-readable media 914 of FIG. 9. The features andtechniques described herein are platform-independent, meaning that theymay be implemented on a variety of commercial computing platforms havinga variety of processors.

Example Device

FIG. 9 illustrates various components of example device 900 that can beimplemented as any type of client, server, and/or computing device asdescribed with reference to the previous FIGS. 1-8 to implementtechniques enabling an application-launching interface for multiplemodes. In embodiments, device 900 can be implemented as one or acombination of a wired and/or wireless device, as a form of televisionclient device (e.g., television set-top box, digital video recorder(DVR), etc.), consumer device, computer device, server device, portablecomputer device, user device, communication device, video processingand/or rendering device, appliance device, gaming device, electronicdevice, and/or as another type of device. Device 900 may also beassociated with a user (e.g., a person) and/or an entity that operatesthe device such that a device describes logical devices that includeusers, software, firmware, and/or a combination of devices.

Device 900 includes communication devices 902 that enable wired and/orwireless communication of device data 904 (e.g., received data, datathat is being received, data scheduled for broadcast, data packets ofthe data, etc.). The device data 904 or other device content can includeconfiguration settings of the device, media content stored on thedevice, and/or information associated with a user of the device. Mediacontent stored on device 900 can include any type of audio, video,and/or image data. Device 900 includes one or more data inputs 906 viawhich any type of data, media content, and/or inputs can be received,such as user-selectable inputs, messages, music, television mediacontent, recorded video content, and any other type of audio, video,and/or image data received from any content and/or data source.

Device 900 also includes communication interfaces 908, which can beimplemented as any one or more of a serial and/or parallel interface, awireless interface, any type of network interface, a modem, and as anyother type of communication interface. The communication interfaces 908provide a connection and/or communication links between device 900 and acommunication network by which other electronic, computing, andcommunication devices communicate data with device 900.

Device 900 includes one or more processors 910 (e.g., any ofmicroprocessors, controllers, and the like), which process variouscomputer-executable instructions to control the operation of device 900and to enabling an application-launching interface for multiple modes.Alternatively or in addition, device 900 can be implemented with any oneor combination of hardware, firmware, or fixed logic circuitry that isimplemented in connection with processing and control circuits which aregenerally identified at 912. Although not shown, device 900 can includea system bus or data transfer system that couples the various componentswithin the device. A system bus can include any one or combination ofdifferent bus structures, such as a memory bus or memory controller, aperipheral bus, a universal serial bus, and/or a processor or local busthat utilizes any of a variety of bus architectures.

Device 900 also includes computer-readable storage media 914, such asone or more memory devices that enable persistent and/or non-transitorydata storage (i.e., in contrast to mere signal transmission), examplesof which include random access memory (RAM), non-volatile memory (e.g.,any one or more of a read-only memory (ROM), flash memory, EPROM,EEPROM, etc.), and a disk storage device. A disk storage device may beimplemented as any type of magnetic or optical storage device, such as ahard disk drive, a recordable and/or rewriteable compact disc (CD), anytype of a digital versatile disc (DVD), and the like. Device 900 canalso include a mass storage media device 916.

Computer-readable storage media 914 provides data storage mechanisms tostore the device data 904, as well as various device applications 918and any other types of information and/or data related to operationalaspects of device 900. For example, an operating system 920 can bemaintained as a computer application with the computer-readable storagemedia 914 and executed on processors 910. The device applications 918may include a device manager, such as any form of a control application,software application, signal-processing and control module, code that isnative to a particular device, a hardware abstraction layer for aparticular device, and so on.

The device applications 918 also include any system components ormodules to implement techniques enabling an application-launchinginterface for multiple modes. In this example, the device applications918 can include windows-based mode module 122, immersive mode module124, and launcher 126.

CONCLUSION

Although embodiments of techniques and apparatuses enabling anapplication-launching interface for multiple modes have been describedin language specific to features and/or methods, it is to be understoodthat the subject of the appended claims is not necessarily limited tothe specific features or methods described. Rather, the specificfeatures and methods are disclosed as example implementations forapplication-launching interface for multiple modes.

1. A computer-implemented method comprising: presenting, in a singleuser interface and at a one time, labels associated with applications oftwo different modes, the labels intermixed within the single userinterface; and responsive to a single selection, causing one of theapplications to launch within its respective mode.
 2. Acomputer-implemented method as described in claim 1, wherein another ofthe applications is currently-executing and further comprising,responsive to another single selection of a label associated with theother, currently-executing application, presenting the other,currently-executing application within its respective mode.
 3. Acomputer-implemented method as described in claim 1, wherein the singleselection is a single mouse click, gesture, or hot key and the singleselection is the same to launch applications of the two different modes.4. A computer-implemented method as described in claim 1, wherein afirst of the two different modes is a windows-based mode and a second ofthe two different modes is an immersive mode.
 5. A computer-implementedmethod as described in claim 1, wherein at least one of the labelsincludes an indicator indicating which of the two different modes theapplication will be launched responsive to the single selection.
 6. Acomputer-implemented method as described in claim 1, wherein: presentinglabels presents at least some of the labels in a group, the labels inthe group associated with applications of the two different modes; thesingle selection is selection of the group; and causing one of theapplications to launch launches all of the applications of the groupresponsive to the single selection of the group.
 7. Acomputer-implemented method as described in claim 6, wherein the labelsin the group are included in the group responsive to explicit selectionto group the labels, the explicit selection received through the singleuser interface.
 8. A computer-implemented method as described in claim6, wherein the labels in the group are included in the group based on ahistory of prior selections received through the single user interface.9. A computer-implemented method comprising: presenting, in a singleuser interface, selectable labels associated with applications, at leastone of the applications associated with a windows-based mode and atleast one of the applications associated with an immersive mode, and aselectable group associated with two or more grouped applications, atleast one of the grouped applications associated with the windows-basedmode and at least one of the grouped applications associated with theimmersive mode; and responsive to selection of one of the selectablelabels, causing the selected application associated with the selectedlabel to launch within its respective mode, or responsive to selectionof the selectable group, causing the grouped applications to launchwithin their respective modes, or enabling selection of each of thegrouped applications and, responsive to selection of a selected groupedapplication, causing the selected grouped application to launch in itsrespective mode.
 10. A computer-implemented method as described in claim9, wherein the selection is of the selectable group and the methodcauses the grouped applications to launch within their respective modes,and further comprising causing the applications to be presented in bothmodes at a same time.
 11. A computer-implemented method as described inclaim 9, further comprising, prior to the act of presenting theselectable group, enabling selection of selectable labels to be placedinto the group.
 12. A computer-implemented method as described in claim9, further comprising launching the grouped applications responsive tologin, resume from a low-power mode, a user-configured trigger, apre-set time, or movement of a computing device that presents theselectable labels.
 13. A computer-implemented method comprising:presenting selectable labels associated with applications, at least oneof the applications associated with a windows-based mode and at leastone of the applications associated with an immersive mode; andresponsive to selection of a selectable label, causing the selectedapplication associated with the selected label to be launched within itsrespective mode.
 14. A computer-implemented method as described in claim13, wherein the selected application is associated with thewindows-based mode and causing the selected application to be launchedlaunches the selected application within the windows-based mode in awindow having a frame, the frame having controls for moving or sizingthe window.
 15. A computer-implemented method as described in claim 13,wherein the selected application is associated with the immersive modeand causing the selected application to be launched launches theselected application within the immersive mode.
 16. Acomputer-implemented method as described in claim 13, wherein at leastone of the selectable labels include an indicator indicating the mode inwhich the application will be launched.
 17. A computer-implementedmethod as described in claim 13, wherein the selection of the selectablelabel is a single mouse click, gesture, or hot key.
 18. Acomputer-implemented method as described in claim 13, further comprisingenabling a same type of selection to select the at least one of theapplications associated with a windows-based mode and the at least oneof the applications associated with an immersive mode.
 19. Acomputer-implemented method as described in claim 13, wherein theselected application is associated with both the windows-based mode andthe immersive mode, further comprising determining which of the modes inwhich to launch the selection application, and wherein causing theselected application to be launched launches the selected applicationwithin the determined mode.
 20. A computer-implemented method asdescribed in claim 13, wherein the selected application is a firstselected application and its respective mode is a first respective mode,and further comprising, responsive to selection of a second selectablelabel, causing a second selected application associated with the secondselected label to be launched within its second respective mode.